From Subroutines to Subsystems : Component - Based Software Development 1
نویسنده
چکیده
In the early days of programming, when machines were hard-wired and every byte of storage was precious, subroutines were invented to conserve memory. Their function was to allow programmers to execute code segments more than once, and under different (parameterized) circumstances, without having to duplicate that code in each physical location where it was needed. Software reuse was born. However, this was a different breed of reuse than we know today: This was reuse to serve the machine, to conserve mechanical resources. Reuse to save human resources was yet to come.
منابع مشابه
Automating Software Reuse with Amphion
The construction of libraries of reusable software components is the standard software engineering solution for improving software development productivity and quality. By encapsulating usable functionality in software components (e.g. subroutines, object classes), and then reusing those components, software of greater functionality can be developed in less time, with some assurance that the ov...
متن کاملSeparate Computation of Alias Information for Reuse 1
Interprocedural data ow information is useful for many software testing and analysis techniques, including data ow testing, regression testing, program slicing, and impact analysis. For programs with aliases, these testing and analysis techniques can yield invalid results, unless the data ow information accounts for aliasing eeects. Recent research provides algorithms for performing interproced...
متن کاملSoftware Components in Contexts and Service Negotiations
Before the term "component" became popular, terms such as subroutine, procedure, function, module, and object have been used from the earliest days of software development to denote software artifacts. Software developers have a subjective understanding of what they mean when speaking of subroutines, procedures, functions, modules, and objects, including a sense of how the meanings are distinct...
متن کاملRevisiting Interacting Subsystems Accounts of Cognitive Architecture: The Emergence of Control and Complexity in an Algebra Task
Symbolic accounts of cognitive architecture most often have a central hub where information is processed (e.g. the production process in ACT-R [1]). An alternative approach is to model cognition as the interaction of multiple largely autonomous subsystems [2, 3]. This latter, Interacting Subsystems, approach is explored in the GLAM-PS cognitive architecture, a theory that operationalizes many o...
متن کاملSeparate Computation of Alias Information fior Reuse
Interprocedural data flow information IS useful for many software testing and analysis techniques, including data flow testing, regression testing, program slicing, and impact analysis. For programs with aliases, these testing and analysis techniques can yield invalid results, unless the data flow information accounts for aliasing effects. Recent research provides algorithms for performing inte...
متن کامل